INT PR

HEADS UP - this branch contains the code of B-21583 so please ensure this does not get merged until after that gets in

Agility ticket

Summary

This has been previously tested using our typical queue backend code, but this new BL is using a db function instead with an addition of amove_to_dest_gbloc view, which will handle all of the unique affiliation filters we need.

This PR has quite a bit of setup so prepare yer butts. Unfortunately the only way to test this thoroughly is to create a metric butt ton of moves.

Per the BL in Agility, we want to add a new "Destination Requests" queue for TOO. This queue will contain moves that are in Approvals Requested status and have the following criteria based on the SHIPMENT'S DESTINATION ADDRESS GBLOC, not the destination duty location on the orders:

• destination SIT requests (in SUBMITTED status)
• shipment destination address requests (in REQUESTED status)
• move is in APPROVALS REQUESTED status

There are these exceptions for USMC customers (service_members.affiliation)

• all USMC moves go into the USMC GBLOC

There are these exceptions for USAF and Space Force customers (service_members.affiliation)

• if the destination address is in Alaska Zone II (re_rate_areas.name) it needs to go to the MBFL GBLOC
• if it is NOT in Alaska Zone II (re_rate_areas.name), it needs to go to the destination address' respective GBLOC
• if the destination address is in Alaska Zone II & the customer is in any other branch (excluding USAF/SF/USMC), the move should be in the JEAT GBLOC

I would highly advise you to set up a tracker doc (I just used the Mac Notes app) so you can mark which GBLOC the moves should be in, as well as move codes, etc. - here's what I did.

USMC:

Move: HHX6VW
GBLOC: USMC
1 Cold St.
Tok, AK 99776
Zone II 
- Dest SIT

Move: VPK7PW
GBLOC: USMC
2 Cold St.
Sitka, AK 99836
Zone IV 
- Dest address

Move: 3P8MHV
GBLOC: USMC
3 Cold St.
Los Angeles, CA 90210
CONUS
- Dest shuttle


USAF:

Move: 6DC3YQ
GBLOC: MBFL
4 Cold St.
Tok, AK 99776
Zone II 
- Dest shuttle

Move: R6849P
GBLOC: MAPK
5 Cold St.
Sitka, AK 99836
Zone IV 
- Dest address

Move: Y7R8BB
GBLOC: KKFA
6 Cold St.
Los Angeles, CA 90210
CONUS
- Dest SIT


SF:

Move: VYMKYT
GBLOC: MBFL
7 Cold St.
Tok, AK 99776
Zone II 
- Dest shuttle

Move: FFD4W4
GBLOC: MAPK
8 Cold St.
Sitka, AK 99836
Zone IV 
- Dest address

Move: QJXY74
GBLOC: KKFA
9 Cold St.
Los Angeles, CA 90210
CONUS
- Dest SIT


ARMY:

Move: 9GCGYQ
GBLOC: JEAT
10 Cold St.
Tok, AK 99776
Zone II 
- Dest shuttle

Move: F7WJHQ
GBLOC: MAPK
11 Cold St.
Sitka, AK 99836
Zone IV 
- Dest address

Move: 4WP9PB
GBLOC: KKFA
12 Cold St.
Los Angeles, CA 99510
CONUS
- Dest SIT

How to test USMC

1. Log in as a customer, set up with a USMC affiliation
2. Create a move with orders that land somewhere in Alaska Zone II
3. Add a shipment(s) (I've just been doing an HHG shipment)
4. Sign and submit
5. Create another move - this time we'll test a move that's NOT in Alaska Zone II (I typically use AK Zone IV)
6. Follow steps 2-4, but use an AK Zone IV ZIP
7. Create another move - this time just do a CONUS move, can be whatever, sign & submit
8. You should now have 3 USMC moves
9. Log in as a USMC SC and approve all 3 USMC moves
10. Log in as USMC TOO and approve all 3 USMC moves
11. Go in as Prime and request destination SIT on the CONUS move
12. Do a destination address & destination shuttle on the other OCONUS moves
13. Go back in as USMC TOO and view the Destination Requests tab
14. You should see all three moves that need destination actions in the USMC destination queue
15. Verify that you can't see the USMC moves in those respective GBLOCs (you'll have to sign in as other GBLOC users - I tend to use Safari for that while keeping Chrome up for the other) - JEAT is for AK Zone II & MAPK is for AK Zone IV

How to test USAF/SF in Alaska Zone II & non-Alaska Zone II

1. Log in as a customer, set up one with USAF affiliation & one with SF affiliation (You'll have to run through these steps twice - one for USAF & one for SF)
2. Create a move with orders that land somewhere in Alaska Zone II
3. Add a shipment(s) (I've just been doing an HHG shipment)
4. Sign and submit
5. Create another move - this time we'll test a move that's NOT in Alaska Zone II (I typically use AK Zone IV)
6. Follow steps 2-4, but use an AK Zone IV ZIP
7. Create another move - this time just do a CONUS move, can be whatever, sign & submit
8. You should now have 3 moves for each USAF & Space Force customer (Zone II, !Zone II, CONUS)
9. Log in as a SC and approve all 6 moves
10. Log in as TOO and approve all 6 moves
11. Go in as Prime and request destination SIT on the CONUS moves
12. Also ensure you do a destination address request & destination shuttle requests on the OCONUS moves
13. Go back in as TOO and view the Destination Requests tab
14. When logged in as a MBFL TOO, you should see AT A MINIMUM, the Alaska Zone II moves (1 for USAF, 1 for SF)
15. Verify that you can see the moves in the destination queues of the GBLOCs you just looked up

How to test remaining queues

1. Log in as a customer, set up with whatever remaining affiliation
2. Create a move with orders that land somewhere in Alaska (testing Zone II for JEAT GBLOC)
3. Add a shipment(s) (I've just been doing an HHG shipment)
4. Sign and submit
5. Create another move - this time we'll test a move that's NOT in Alaska Zone II
6. Follow steps 3-4
7. Create another move - this time just do a CONUS move, can be whatever, sign & submit
8. You should now have 3 moves (Zone II, !Zone II, CONUS)
9. Log in as a SC and approve all 3 moves
10. Log in as TOO and approve all 3 moves
11. Go in as Prime and request destination SIT on the CONUS move
12. Also ensure you do a destination address request and destination shuttle on the OCONUS moves
13. Go back in as a JEAT TOO and view the Destination Requests tab
14. You should AT A MINIMUM, see the Alaska Zone II move (since it is not USAF/SF/USMC and in Alaska Zone II)
15. Verify that you can see the moves in the destination queues of the GBLOCs you just looked up

Additional testing

1. Since this queue does not use existing functionality and uses a database function, play with the queue
2. Confirm you can search, filter, and just generally try to break it
3. Test thoroughly as this is likely what we will be converting other queues to in order to reduce database calls and make the app a little more efficient

Screenshots